Rich object model for diverse Auto-ID tags

ABSTRACT

A system and method allowing one application to implement diverse AutoID tags interchangeably, by unifying all AutoID technologies into a single object model. The single object model interacts with all AutoID technologies, with only a lowest level device tailored to the specific AutoID technology, the single object model thereby persisting through the middleware, up to an application, carrying all necessary information from any AutoID technology. The single object model can interact with a tag many times, as necessary to complete an operation. A reader interface allows an application to communicate with multiple readers of diverse AutoID tags, and to communicate with individual servers communicating with individual readers of diverse AutoID tags. The reader interface also provides a single interface for hardware communication with a radio, for an application interacting with an entire network of readers, sensors, interpretation steps, product lookup, and information storage providing a single virtual reader.

RELATED APPLICATIONS

This application is a continuation of the U.S. patent application Ser.No. (not yet assigned), entitled RICH OBJECT MODEL FOR DIVERSE AUTO-IDTAGS, filed Jun. 20, 2005, in the name of Steven A. N. Shafer; whichapplication is incorporated herein by reference.

FIELD OF THE INVENTION

The present invention is directed to a system and methods forimplementing diverse AutoID tags.

BACKGROUND OF THE INVENTION

There are many types of AutoID tags in use today including bar codes,magnetic stripe cards, smartcards, contactless smart cards, RFID, sensornodes, and others. Today, some applications are specific to a particulartechnology (usually a particular manufacturer). If a device in aparticular technology includes unique features, the middlewareunderstands the unique features because of the single applicationwritten for the device. The application can use the unique featuresbecause the application, the middleware and the device all correspond toan identical model of the unique features.

Other applications, corresponding to most systems is use today, aregeneric for many kinds of AutoID tags, providing many device types andapplications, but communication of data in these applications is reducedto a lowest common denominator, preserving only an identification numberof a given AutoID tag. That is, all capabilities of respective devicesin these systems are abstracted or extracted away, with only theidentification (ID) number or string being communicated from a device toan application. Generic applications cannot exercise other features ofAutoID tags such as writable memory, security handshaking, attachedsensors or other devices, etc.

What is needed is the ability to provide a given application acapability of using many different forms of AutoID tags interchangeably.What is needed is an IDTag object model in middleware capable ofpropagating a model of unique features to respective applications.Accordingly, many different applications could advantageously use thefeatures based on a description of the features, or based on adescription of specific pieces of hardware that implement the features.

SUMMARY OF THE INVENTION

The present invention is directed to a system and method forimplementing diverse AutoID tags. The present invention overcomes thedrawbacks and shortcomings of the prior art by providing a capabilitythat allows the same compiled application to use many different forms ofAutoID tags interchangeably. For example, a single inventory applicationsystem could write an ID number and owner's name onto a ‘tag’ whetherthat tag is RFID, magnetic stripe, or a custom IR badge, as long as thetag has available memory. Accordingly, the present invention allowsapplications to exercise features for writable memory and securityinteractions in a technology-independent way. The invention also exposesother hardware-specific features in a unified framework.

The present invention unifies all AutoID technologies into a singleobject model, so that a single program can be written to interact withall of the technologies, and only a lowest level device in a system needbe tailored to the specific technology of the AutoID device. Once anobject model and IDTag is fulfilled, then an object model can persistall the way through the middleware, up to an application, and can carrynecessary information from any of the AutoID technologies.

One aspect of the present invention is an IDTag model, which is anobject model representing any one of the AutoID technology units. Forexample, one representation or observation of a barcode label, onerepresentation of a RFID tag reading, etc. The IDTag object model canalso persist for interaction with a tag many times, which often occursbefore an operation is complete. For example, the presence of an AutoIDtag is detected, and an IDTag object instance is created. Perhaps latermore data is required from a tag; the IDTag object model can be examinedto see if the required data is there, if not, a reader is instructed toread the additional data, and the additional data is inserted into theIDTag object model for future use. Accordingly, the IDTag object modelrepresents one physical object, and can persist over many uses.

Another aspect of the invention is a reader interface, also referred toas a Virtual Reader, which is an abstract description of an interface toa reader device, or a software process conceptualizing multiple readerdevices or large scale sensors. Accordingly, the reader interface of thepresent invention allows an application to communicate with a wholeassembly, having multiple readers of diverse Auto ID tags, and also tocommunicate with each individual server that communicates with eachindividual reader in the whole assembly.

Generally, different interfaces are used at different levels of asystem. The reader interface of the present invention also provides thata single interface can be used from a hardware that communicates with aradio, all the way up to an application interacting with an entirenetwork of sensors, interpretation steps, product lookup, andinformation storage all compiled together to implement one “virtualreader” whose reports are not raw tag data, but are actuallyhighly-processed, smooth filtered, aggregated data.

BRIEF DESCRIPTION OF THE DRAWINGS

The foregoing summary, as well as the following detailed description ofillustrative embodiments, is better understood when read in conjunctionwith the appended drawings. For the purpose of illustrating theinvention, there is shown in the drawings example constructions of theinvention; however, the invention is not limited to the specific methodsand instrumentalities disclosed. In the drawings:

FIG. 1 is a block diagram showing an example computing environment inwhich aspects of the invention may be implemented;

FIG. 2 illustrates two models provided in current IDTag interoperabilitysystems for interacting between a device and an application;

FIG. 3 introduces a third model to FIG. 2, the model including manydevice types having unique features, and where an IDTag object model inthe middleware propagates a model of the unique features to respectiveapplications;

FIG. 4 illustrates an IDTag object model of the present invention, whichallows middleware to perform event detection and filtering, and to passdetection events and read/write/control commands between tag readers andapplications;

FIG. 5 illustrates an IDTag and an associated IDTag Template of thepresent invention, where the IDTag Template describes tag parts andcapabilities, and where one template exists for each type of tag;

FIG. 6 illustrates IDTag Template deployment of the present invention;

FIG. 7 illustrates scanning activities associated with the presentinvention, and the elements included in the scanning activities;

FIG. 8 illustrates one of many approaches associated with the presentinvention for deriving location information from an IDTag reading, theapproach of FIG. 8 assigning a name or ID to each reader;

FIG. 9 illustrates another approach for deriving location informationfrom an IDTag reading, the approach of FIG. 9 using location checktagsto distinguish tags at known locations;

FIG. 10 illustrates another approach for deriving location informationusing Trilateration;

FIG. 11 illustrates another approach for deriving location informationusing signal strength signature, where signal strength is measured byseveral readers, and a look up process is implemented rather than acalculation process;

FIG. 12 illustrates still another approach associated with the presentinvention for deriving location information, implementing a beacon thatbroadcasts identification information to readers;

FIG. 13 implements tags with location sensors for deriving locationinformation, where a tag may be used for telemetry, and RFID is acarrier of sensor data to a reader and an application;

FIG. 14 implements a specialized antenna, or collection of antennas, toimplement differential times of flight techniques to determine thelocation of a tag;

FIG. 15 illustrates an overall system model of the present invention,indicating that many entities can affect the middleware, and indicatinga mechanism to incorporate constraints of different programming devices,or filters, into the system model;

FIG. 16 illustrates an interface provided by the present invention forinteraction between a provider of ID reports and a consumer of the IDreports;

FIG. 17 illustrates a programming device of the present invention actingas a filter to provide event cleanup;

FIGS. 18-22 illustrate various tasks accomplished through use ofprogramming devices, or filters, of the present invention, such asproduct look up, configuration information hiding hardware details,buffering data, producing statistics and traffic reports, andaggregating multiple readers to look like one single reader at a virtuallevel;

FIG. 23 illustrates one embodiment of a filter-based architecture of thepresent invention, showing development of an enterprise scale system,where filters are a primary building block for an RFID applicationinterface; and

FIG. 24 illustrates a drop through design for filter stacks, inaccordance with the present invention, where a top level filter candispatch an operation directly down to a respective lower level filterthat will implement the operation, thereby skipping all intermediatefilter levels.

DETAILED DESCRIPTION OF ILLUSTRATIVE EMBODIMENTS

Example Computing Environment

FIG. 1 and the following discussion are intended to provide a briefgeneral description of a suitable computing environment in which anexample embodiment of the invention may be implemented. It should beunderstood, however, that handheld, portable, and other computingdevices of all kinds are contemplated for use in connection with thepresent invention. While a general purpose computer is described below,this is but one example. The present invention also may be operable on athin client having network server interoperability and interaction.Thus, an example embodiment of the invention may be implemented in anenvironment of networked hosted services in which very little or minimalclient resources are implicated, e.g., a networked environment in whichthe client device serves merely as a browser or interface to the WorldWide Web.

Although not required, the invention can be implemented via anapplication programming interface (API), for use by a developer ortester, and/or included within the network browsing software which willbe described in the general context of computer-executable instructions,such as program modules, being executed by one or more computers (e.g.,client workstations, servers, or other devices). Generally, programmodules include routines, programs, objects, components, data structuresand the like that perform particular tasks or implement particularabstract data types. Typically, the functionality of the program modulesmay be combined or distributed as desired in various embodiments.Moreover, those skilled in the art will appreciate that the inventionmay be practiced with other computer system configurations. Other wellknown computing systems, environments, and/or configurations that may besuitable for use with the invention include, but are not limited to,personal computers (PCs), automated teller machines, server computers,hand-held or laptop devices, multi-processor systems,microprocessor-based systems, programmable consumer electronics, networkPCs, minicomputers, mainframe computers, and the like. An embodiment ofthe invention may also be practiced in distributed computingenvironments where tasks are performed by remote processing devices thatare linked through a communications network or other data transmissionmedium. In a distributed computing environment, program modules may belocated in both local and remote computer storage media including memorystorage devices.

FIG. 1 thus illustrates an example of a suitable computing systemenvironment 100 in which the invention may be implemented, although asmade clear above, the computing system environment 100 is only oneexample of a suitable computing environment and is not intended tosuggest any limitation as to the scope of use or functionality of theinvention. Neither should the computing environment 100 be interpretedas having any dependency or requirement relating to any one orcombination of components illustrated in the exemplary operatingenvironment 100.

With reference to FIG. 1, an example system for implementing theinvention includes a general purpose computing device in the form of acomputer 110. Components of computer 110 may include, but are notlimited to, a processing unit 120, a system memory 130, and a system bus121 that couples various system components including the system memoryto the processing unit 120. The system bus 121 may be any of severaltypes of bus structures including a memory bus or memory controller, aperipheral bus, and a local bus using any of a variety of busarchitectures. By way of example, and not limitation, such architecturesinclude Industry Standard Architecture (ISA) bus, Micro ChannelArchitecture (MCA) bus, Enhanced ISA (EISA) bus, Video ElectronicsStandards Association (VESA) local bus, and Peripheral ComponentInterconnect (PCI) bus (also known as Mezzanine bus).

Computer 110 typically includes a variety of computer readable media.Computer readable media can be any available media that can be accessedby computer 110 and includes both volatile and nonvolatile, removableand non-removable media. By way of example, and not limitation, computerreadable media may comprise computer storage media and communicationmedia. Computer storage media includes both volatile and nonvolatile,removable and non-removable media implemented in any method ortechnology for storage of information such as computer readableinstructions, data structures, program modules or other data. Computerstorage media includes, but is not limited to, random access memory(RAM), read-only memory (ROM), Electrically-Erasable ProgrammableRead-Only Memory (EEPROM), flash memory or other memory technology,compact disc read-only memory (CDROM), digital versatile disks (DVD) orother optical disk storage, magnetic cassettes, magnetic tape, magneticdisk storage or other magnetic storage devices, or any other mediumwhich can be used to store the desired information and which can beaccessed by computer 110. Communication media typically embodiescomputer readable instructions, data structures, program modules orother data in a modulated data signal such as a carrier wave or othertransport mechanism and includes any information delivery media. Theterm “modulated data signal” means a signal that has one or more of itscharacteristics set or changed in such a manner as to encode informationin the signal. By way of example, and not limitation, communicationmedia includes wired media such as a wired network or direct-wiredconnection, and wireless media such as acoustic, radio frequency (RF),infrared, and other wireless media. Combinations of any of the aboveshould also be included within the scope of computer readable media.

The system memory 130 includes computer storage media in the form ofvolatile and/or nonvolatile memory such as ROM 131 and RAM 132. A basicinput/output system 133 (BIOS), containing the basic routines that helpto transfer information between elements within computer 110, such asduring start-up, is typically stored in ROM 131. RAM 132 typicallycontains data and/or program modules that are immediately accessible toand/or presently being operated on by processing unit 120. By way ofexample, and not limitation, FIG. 1 illustrates operating system 134,application programs 135, other program modules 136, and program data137. RAM 132 may contain other data and/or program modules.

The computer 110 may also include other removable/non-removable,volatile/nonvolatile computer storage media. By way of example only,FIG. 1 illustrates a hard disk drive 141 that reads from or writes tonon-removable, nonvolatile magnetic media, a magnetic disk drive 151that reads from or writes to a removable, nonvolatile magnetic disk 152,and an optical disk drive 155 that reads from or writes to a removable,nonvolatile optical disk 156, such as a CD ROM or other optical media.Other removable/non-removable, volatile/nonvolatile computer storagemedia that can be used in the example operating environment include, butare not limited to, magnetic tape cassettes, flash memory cards, digitalversatile disks, digital video tape, solid state RAM, solid state ROM,and the like. The hard disk drive 141 is typically connected to thesystem bus 121 through a non-removable memory interface such asinterface 140, and magnetic disk drive 151 and optical disk drive 155are typically connected to the system bus 121 by a removable memoryinterface, such as interface 150.

The drives and their associated computer storage media discussed aboveand illustrated in FIG. 1 provide storage of computer readableinstructions, data structures, program modules and other data for thecomputer 110. In FIG. 1, for example, hard disk drive 141 is illustratedas storing operating system 144, application programs 145, other programmodules 146, and program data 147. Note that these components can eitherbe the same as or different from operating system 134, applicationprograms 135, other program modules 136, and program data 137. Operatingsystem 144, application programs 145, other program modules 146, andprogram data 147 are given different numbers here to illustrate that, ata minimum, they are different copies. A user may enter commands andinformation into the computer 110 through input devices such as akeyboard 162 and pointing device 161, commonly referred to as a mouse,trackball or touch pad. Other input devices (not shown) may include amicrophone, joystick, game pad, satellite dish, scanner, or the like.These and other input devices are often connected to the processing unit120 through a user input interface 160 that is coupled to the system bus121, but may be connected by other interface and bus structures, such asa parallel port, game port or a universal serial bus (USB).

A monitor 191 or other type of display device is also connected to thesystem bus 121 via an interface, such as a video interface 190. Inaddition to monitor 191, computers may also include other peripheraloutput devices such as speakers 197 and printer 196, which may beconnected through an output peripheral interface 195.

The computer 110 may operate in a networked environment using logicalconnections to one or more remote computers, such as a remote computer180. The remote computer 180 may be a personal computer, a server, arouter, a network PC, a peer device or other common network node, andtypically includes many or all of the elements described above relativeto the computer 110, although only a memory storage device 181 has beenillustrated in FIG. 1. The logical connections depicted in FIG. 1include a local area network (LAN) 171 and a wide area network (WAN)173, but may also include other networks. Such networking environmentsare commonplace in offices, enterprise-wide computer networks, intranetsand the Internet.

When used in a LAN networking environment, the computer 110 is connectedto the LAN 171 through a network interface or adapter 170. When used ina WAN networking environment, the computer 110 typically includes amodem 172 or other means for establishing communications over the WAN173, such as the Internet. The modem 172, which may be internal orexternal, may be connected to the system bus 121 via the user inputinterface 160, or other appropriate mechanism. In a networkedenvironment, program modules depicted relative to the computer 110, orportions thereof, may be stored in the remote memory storage device. Byway of example, and not limitation, FIG. 1 illustrates remoteapplication programs 185 as residing on memory device 181. It will beappreciated that the network connections shown are exemplary and othermeans of establishing a communications link between the computers may beused.

One of ordinary skill in the art can appreciate that a computer 110 orother client devices can be deployed as part of a computer network. Inthis regard, the present invention pertains to any computer systemhaving any number of memory or storage units, and any number ofapplications and processes occurring across any number of storage unitsor volumes. An embodiment of the present invention may apply to anenvironment with server computers and client computers deployed in anetwork environment, having remote or local storage. The presentinvention may also apply to a standalone computing device, havingprogramming language functionality, interpretation and executioncapabilities.

The Present Invention

The term AutoID, in the present invention, refers to any technologyinvolving small mobile labels having some identification characteristiccapable of being read by a sensor and fed into a computer system. AutoIDincludes barcodes, magnetic stripe cards, smartcards, contact withsmartcards, RFID, even “blue tooth” devices, and may include otherrelated or similar devices.

The present invention unifies all AutoID technologies into a singleobject model, so that a single program can be written to interact withall of the technologies, and only a lowest level device in a system needbe tailored to the specific technology of the AutoID device. Once anobject model and IDTag is fulfilled, then an object model can persistall the way through the middleware, up to an application, and can carrynecessary information from any of the AutoID technologies.

The present invention can roughly be divided into two parts. One part isthe IDTag model, which is the object model representing any one of theAutoID technology units. For example, one representation or observationof a barcode label, one representation of a RFID tag reading, etc. Butthe IDTag object model also persists for interaction with a tag manytimes, which often occurs before an operation is complete. For example,the presence of an AutoID tag is detected, and an IDTag object instanceis created. Perhaps later more data is required from a tag; the IDTagobject model can be examined to see if the required data is there, ifnot, a reader is instructed to read the additional data, and theadditional data is inserted into the IDTag object model for future use.Accordingly, the IDTag object model represents one physical object, andcan persist over many uses.

The second part of the invention is a reader interface, referred to asIIDTagReporter interface. The IIDTagReporter interface may also bereferred to as a Virtual Reader, in that it is an abstract descriptionof an interface to a reader device, or a software processconceptualizing multiple reader devices or large scale sensors. Forexample, an institution might have 100 readers, the data from all thesereaders could be sent to a central processing facility where anapplication might view the data as coming from “one virtual reader.”With the present invention, the application could use the same abstractinterface to communicate with a whole assembly, and with each individualserver that communicates with each individual reader.

Generally, different interfaces are used at different levels of asystem. IIDTagReporter provides that a single interface can be used froma hardware that communicates with a radio, all the way up to anapplication interacting with an entire network of sensors,interpretation steps, product lookup, and information storage allcompiled together to implement one “virtual reader” whose reports arenot raw tag data, but are actually highly-processed, smooth filtered,aggregated data.

FIG. 2 illustrates two models provided in current systems forinteracting between a device and an application. One model includes adevice with unique features, and a single application written for thedevice, with middleware understanding the unique features. Theapplication can use the unique features because the application, themiddleware and the device all correspond to an identical model of theunique features. The second model illustrated, which corresponds to mostcurrent systems, provides many device types and many applications, butcommunication of data is reduced to a lowest common denominator. Thatis, all capabilities of the respective devices are abstracted orextracted away, except an identification (ID) number or string. Only theID is communicated from a device to an application. If a device haswritable memory, that would not be communicated. If the device hassecurity mechanisms, they would not be reflected in the application. Ifthe device has sensors attached, they would not be communicated. Anyunique feature included in a device would not pass through themiddleware, and would not be exposed to the application.

FIG. 3 introduces a third model (in the center) of ID Taginteroperability, which includes many device types having uniquefeatures, and where an IDTag object model in the middleware propagates amodel of the unique features to respective applications. Accordingly,many different applications can advantageously use the features based ona description of the features (i.e., a description of specific pieces ofhardware that implement the features). The present invention providesthis operability.

IDTag Object Model

This section presents uses and design for an object model of ID(identification) tags of the present invention, called IDTag. This modelis intended to represent ID tags of all varieties, including RFID (RadioFrequency Identification) tags; SmartCards and NFC; bar codes; magneticstripe codes; and any similar labels. The IDTag model allows all ID tagtechnologies to be processed by the same middleware software.

IDTags are self-describing enough to allow middleware to propagate them,sort them, perform event filtering, etc. However, in some embodiments,the level of self-description does not allow middleware to “discover”advanced tag control paradigms at run-time. If tags have advancedcapabilities, such as attached sensors, it is assumed that theapplication will already know how to exercise these capabilities. TheIDTag in these cases merely carries the representation between thedevice driver and the application.

Referring now to FIG. 4, the IDTag object model allows middleware toperform event detection and filtering, and to pass detection events andread/write/control commands between tag readers and applications, forall types of ID tags including RFID, bar codes, SmartCards, etc.

The IDTag of the present invention includes enough explicit informationto support event filtering, writable memory, and security keys; and topass through more exotic operations (reading and writing sensors, uniquehardware features, 2-way data exchange). However, for such “exotic”operations, the application and the reader driver must agree on how touse the IDTag object model to perform effective communication. In thesecases, in certain embodiments of the invention, the IDTag-basedmiddleware simply passes the operations and data back and forth asneeded. The middleware is not expected to understand exotic operationsnor how they are encoded in the IDTag. In this way, common middlewarecan be used for all types of ID tags, and different types of tags caneven be mixed in the same event streams, etc.

In certain aspects of the invention, the IDTag object model is not aimedat supporting all features of all ID tag technologies; for instance,where a single type of device is talking to a single application. Suchdevice-dependent applications might choose a different representation.However, even in these cases, the IDTag model proves useful as aframework for communication.

Aspects of the Invention

In certain aspects of the invention, the IDTag object model:

-   -   enables a compiled program (middleware or application) to        process many kinds of ID tags.    -   accommodates ID fields representing characters (Unicode) or        bitstrings, of arbitrary length.    -   enables many kinds of ID tags to coexist and to be mixed within        a single data stream or data store.    -   provides very efficient processing of ID data from ID tags,        particularly for the operations of comparing, copying, sorting,        and hashing.    -   provides configuration available in a template that describes        the overall characteristics of the tag, expressible in XML so        that an XML file can be distributed and loaded to create an        object model of the template in an application at run-time.    -   is expressible in UML, XML, as a CLR object, and as a SQL        schema.    -   includes a mechanism for handling “Alias IDs” that are randomly        generated (typically followed by security authorization and        actual ID transmission).    -   provides a mechanism so that all significant tag types and        features carry both a name (for identification) and description        (for explanation).

In certain aspects of the invention directed to RFID Technologies, theIDTag:

-   -   represents all the key capabilities for EPCglobal RFID tags.    -   represents the key capabilities for representative legacy        (pre-EPCglobal) passive and active RFID tags, both standard        (ISO, AIAG, etc.) and manufacturer-specific.    -   represents user-writable memory, including memory that is        partitioned into multiple blocks, and memory that can be blocked        from writing.    -   carries sufficient information to allow an application to invoke        operations on tags with sensors and/or other devices attached,        particularly for reading, writing, and control functions.    -   accommodates future security regimens that utilize keys        (passwords) of arbitrary length, with multiple keys for various        purposes. Since the purposes cannot be known in advance, an        arbitrary number of keys must be supported, with an identifier        for each to denote its role.

In certain aspects of the invention directed to SmartCards and NFCIP,the IDTag

-   -   represents SmartCards or NFCIP tags, according to the ISO 14443        protocol or the ECMA NFCIP-1 or NFCIP-2 protocols.    -   carries sufficient information to allow an application to invoke        all key operations on SmartCards and NFC cards, including        security functions and data transfers.    -   carries sufficient information to allow a full implementation of        relevant aspects of PC/SC and (U.S.) Government Interoperable        Smart Card specifications.

In certain aspects of the invention directed to Bar Codes, the IDTag

-   -   represents bar codes of any length, using any symbology and any        physical encoding.    -   represents Bar codes as Unicode strings of arbitrary length.

In certain aspects of the invention directed to Magnetic Stripe Cards,the IDTag

-   -   represents magnetic stripe cards obeying the ISO 7810        specification, Formats A and B.

In certain aspects of the invention directed to Distributed SensorNetworks, the IDTag

-   -   represents nodes in a distributed sensor network, including        motes, gateways, and micro-servers.

In certain aspects of the invention directed to IHV Extensions, theIDTag

-   -   provides a way for a hardware vendor to expose state information        and control functions beyond those provided in standard ID tag        representations.        Design

An IDTag represents a single tag. An IDTagTemplate represents a type oftag, for example “EPCglobal Class 1”. As illustrated in FIG. 5, an IDTagfollows a pattern described in an IDTagTemplate. Each major component ofthe IDTag is represented by a separate object (IDTag, ID, DataPort,SecurityKeySet, SecurityKey); and each of these has a correspondingtemplate object (IDTagTemplate, IDTemplate, DataPortTemplate,SecurityKeySetTemplate, and SecurityKeyTemplate). The IDTag object andeach of its components has a link to the corresponding template object.

Accordingly, the template contains information about a configuration ofthe tag, allowing an application to effectively take advantage offeatures of the tag, to determine whether the tag has features aparticular application requires, whether the tag may allow theapplication to select a particular way of encoding data orcommunications with the tag and/or to accommodate the hardware on thattag. For example, an application might require 500 bytes of memory onthe tag. One kind of tag might not have that much memory. So theapplication could determine that by examining the template. Another kindof tag might have way too much memory. So the application could simpleread and write in blocks of 500. Another tag might have enough memory,but its broken into blocks of 100 bytes each. So the application wouldneed to read and write five separate blocks to store all of the data.

Further, most readers can only read one type of tag. So, that readerwould have one tag template and that tag template object would be storedin the reader and when the reader makes reports about tags, it wouldreport the template along with the tag. It only needs to report thetemplate once, because once the application knows the template, theapplication can interpret all subsequent reports received from thereader about a tag via a pointer instructing the application to whichtemplate describes the tag type. Some readers can in fact recognize morethan one kind of tag, so a reader could recognize and communicate tagsthat have more than one template. Each template has a name, and thatname is the string used to associate the tag with a template from readerto server to an application. So for each element of the IDTag ObjectModel, there is an corresponding element named with a template suffix.

The IDTag Template forms a complete object model on its own.Furthermore, there is a specified way of serializing the IDTag Templateinto an XML description. Having a description of the tag in XML form,one hardware vendor might encode the templates directly into the readerso that the reader comes with the templates embedded. Referring now toFIG. 6, another hardware vendor might point to a standards bodycontrolling the XML schema, the enterprise retrieving the schema fromthe standards body. In any case, the schemas can be kept in a repositoryof the enterprise, or in the readers, and the upper layers of softwarecan retrieve the template either from the lower layers of software, orfrom the central repository of the enterprise. You can imagine thatdifferent pieces of hardware have features, and imagine that some ofthose features are more exotic, more unique more bizarre and others aremore generic. So if you reduce all tags to a simple ID number, what yoursaying is that you're only going to take the most generic feature andreduce everything to that. Some systems of middleware include a littlebit of unique feature. ID Tag goes much further and includes many moreunique features. But it still has a cut-off, and beyond that cut-off itsnecessary to fall back on some sort of pass-through which is beyond thescope of the ID tag object model. So that takes through the first andsecond major bullet items. Now lets talk about the third one which isalias IDs.

Design of IDTag Class

The IDTag represents a single tag. It comprises an ID, zero or moreDataPorts of two types (ControlPorts and MemoryPorts), and aSecurityKeySet for the tag and its ID field. The design of eachcomponent is described in following sections.

In addition, several other properties can be included, such as:

-   -   CurrentAliasID is used to handle secure IDTags that do not        reveal their actual ID on first contact. Each time they are        scanned, such cards generate a random number (called the “Alias        ID” in the IDTag SDK). To determine the actual ID, the reader        device must supply a password to the tag; if accepted, the tag        will then allow the reader to query for the actual ID.        CurrentAliasID is used to record the Alias ID currently in        effect for the tag; when a new scan is initiated, the        CurrentAliasID should be discarded. CurrentAliasID is used if        and only if the corresponding IDTagTemplate has a non-null        AliasIDDescription property.        -   Note that some tags have only Alias IDs and have no actual            ID at all; some middleware may be unable to process them.            Example: ISO 18092 cards.    -   IsDescribed is a boolean that tells whether the following        properties of the tag are all valid. For some tags, the tag must        actually be queried separately for some or all of the following        information; if so, then the reader would initially set        IsDescribed to false. This tells applications that they must        perform a Describe operation (see the IIDTagReporter interface)        before querying for the following properties of the tag. The        IIDTagReporter responsible for the tag should also perform such        description automatically if one of the following properties is        queried while IsDescribed is false. (Note that for many tags,        the IDTagTemplate has all necessary details, so IsDescribed will        always be set to true.). In other embodiments of the invention,        a separate IsDescribed field is provided for each of the        following properties, rather than just one field for the entire        tag object    -   TagDetails is a string to contain manufacturer's details about        the tag. Different tags may use this string differently.    -   IsDeactivated indicates whether this tag is known to be        deactivated. (It may be best to discard the IDTag object        completely.) This property is meaningful only if the        IDTagTemplate has IsDeactivatable set to true.    -   Some tags allow the ID field itself to be written by the reader;        and some of these tags further allow the reader to “write-lock”        the ID to prevent subsequent changes. IsIDWriteLocked indicates        whether the ID field on this tag has been so protected. It is        only meaningful if the corresponding IDTagTemplate has both        IsIDWritable and IsIDWriteLockable set to true.        Design of the IDTagTemplate Class

In addition to the properties described above, the IDTagTemplate caninclude the following components:

-   -   A name (such as “EPCglobal Class 0”) and a description suitable        for longer display (such as in a ToolTip popup).    -   A set of communication protocols, denoted by strings, which may        be used to communicate with tags of this type. (Example: For        RFID tags, these would be the names of air protocols.) All        settings required by the reader are assumed to be implied by the        designation of a protocol, for example if a protocol has        different parameters in the US and Europe, each parameter        setting would be a separate “protocol” in the IDTagTemplate.    -   The number of “control operations” defined for this type of tag.    -   A Boolean to indicate whether this type of tag can be        deactivated.        Design of the ID Class

IDs can be binary (as in most electronic ID tags) or character strings(as in most printed ID tags). Both require efficient processing for thefundamental operations of comparing, hashing, and copying. An ID can becreated with either a binary (unsigned 32-bit int array) or stringvalue. WordString is a class that represents either type of valueefficiently; ID is a subclass of WordString.

-   -   If created with a binary value, comparisons etc. will be fast        using the binary representation, and the string equivalent is        available on demand (formatted as desired). The IsString        property of the IDTemplate will be false.    -   If created with a string, comparisons etc. will take place using        string functions. The IsString property of the IDTemplate will        be true.

Additional operations on the ID include generating a random ID andincrementing the value by 1; these operations can be useful fordebugging software.

ID is a subclass of WordString that adds a Name string and a Descriptionstring.

Representing Binary ID Values in the ID Class

For efficient processing, a binary ID value is represented as an arrayof unsigned 32-bit “words”. The reader driver software is expected toconvert the actual internal representation into this representation whenreporting the IDs of scanned tags. The length of the array is given inthe IDTemplate (ExpectedLength) unless it is variable-length(IsVariableLength is true).

All bits are considered meaningful for hashing, comparison, etc. Anymeaningless bits should be set to 0 by the reader software, before theID data is placed into an ID object instance. If there are meaninglessbits in the middle of the meaningful bits, the reader software may shiftthe meaningful bits to eliminate the internal zero-padding bitsaltogether.

If the number of bits is not a multiple of 32, then the preferredrepresentation is that all the most significant (lowest-indexed) wordscontain 32 meaningful bits, beginning with the most significant bits ofthe ID, and the last (highest-indexed) word contains the remaining bits.In any word that contains less than 32 meaningful bits, the preferredrepresentation is that the least significant bits of the word aremeaningful, i.e. the data should be right-shifted and padded with 0 bitson the left.

Generally, the authority responsible for the IDTemplate (e.g. the XMLfile containing the IDTemplate definition) will also be responsible forissuing the representation rules for ID fields using that IDTemplate.

Comparing ID Values

If IDs have different IDTemplates, then they are ordered according tothe Name property of their respective IDTemplates (i.e. two ID objectscalled ID-A and ID-B are ordered according to the ordering ofID-A.IDTagTemplate.Name and ID-B.IDTagTemplate.Name).

If the IDs have the same IDTemplate but are variable-length withdifferent lengths, the shorter one is considered to be “first” in order.

ID values with the same IDTemplate and length are compared (if string)using string comparison; or (if binary) using word-by-word comparison oftheir (unsigned 32-bit) word values, beginning with the most significantword (index=0).

Lazy Interaction

There are two ways of representing information stored in an object or ina data object. One is explicitly as a field in the data object. Theother is implicitly; that is, the data object does not contain theinformation, but implements a rule or a process by which the informationcan be calculated from data stored explicitly elsewhere. For example, ifstoring the area of a rectangle, the area could be computed and stored;or the length and width could be stored and with the area computed, whenneeded.

A problem can arise with explicit storage, as many quantities requirepre-computing, whether or not the quantities are ever needed. Thesequantities also require storage space in the object. However, explicitstorage provides great speed in retrieval. Accordingly, there is a costwhen creating the object, but there is a speed when retrieving theinformation.

Conversely, implicit storage can be problematic, as retrieval is slower.Implicit storage does provide the benefit of avoiding a cost, duringobject creation, of computing quantities not required. The slowretrieval results from the effort expended, at data retrieval, ofcalculating the information requested. Further, if retrieving a givendata ten times, the data must be calculated ten times.

Lazy interaction provides that if a field is available in an object tostore a given data, the calculation is not actually performed until thefirst time that data is requested. Lazy interaction avoids theexpenditure of time necessary to calculate data until there is at leastone request, then the given data is stored in a respective field. So,Lazy interaction provides fast creation and fast retrieval.

Lazy interaction has been extended to the present invention for RFIDcommunication. In RFID communication, time on the airwaves can be ascarce resource. Time on the airwaves, as used herein, is communicationairtime between readers and tags. Time on the airwaves requiresscheduling and management for efficiency; it being undesirable toperform unnecessary communication with a tag. If an application does notrequire a given data, expending airtime to request that data from a tagis to be avoided, especially considering that this effort might beduplicated for thousands of tags being processed. With some tagtechnologies, an initial report to a reader might include only a subsetof their total information. So, if more information about a tag isdesired, additional and sometimes repeated communication with the tag isrequired.

Lazy interaction provides that the IDTag object model stores fieldscapable of holding all data needed to describe the tag. A request for agiven data is not actually made unless needed by an application. Oncerequested, the given data is stored in a respective field for later useif repeatedly needed, the motivation being to reduce airtime ofcommunication rather than to reduce processing time.

Design of Data Port Class

An IDTag can have zero or more Control Data Ports and zero or moreMemory Data Ports, as defined in the IDTagTemplate. A data portrepresents a block of data that can be sent (written) to the tag and/orreceived (read) from the tag. The basic operations on a data port areRead and Write.

-   -   A Control Data Port is one that has a special meaning to the        hardware, such as special configuration bits in the tag, or a        communication channel for bulk data exchange, or a sensor whose        value can be read. Reading and writing a Control Data Port        frequently causes behavior changes in the tag, or has side        effects such as reading a sensor. Use of Control Data Ports is        hardware-specific.    -   A Memory Data Port is available for applications to utilize as a        (usually writable) store on the tag. The behavior of the tag is        unaffected by reading and writing a Memory Data Port. Use of        Memory Data Ports is generic across all types of tag (if they        have such memory).

Each data port has a DataPort and a corresponding DataPortTemplate. Mosttags have a fixed number of Control and Memory data ports, but some tagshave a variable number (IsVariableControlPortCount andIsVariableMemoryPortCount in the IDTagTemplate). If the number isvariable, the IDTag itself presents its (current) number of ports inControlPortCount and MemoryPortCount.

The IDTag has an array of DataPorts for control data ports, and anotherarray for memory data ports. Applications will refer to these ports bytheir index in the corresponding array. Each port normally has a uniquecorresponding DataPortTemplate.

-   -   Some tags allow a variable number of ports, with a generic        description for some or all of them. In the IDTagTemplate, the        lower-numbered ports are each described with a unique entry in        the ControlPortTemplate or MemoryPortTemplate array (as        appropriate). For higher-numbered ports the description is given        by the OtherControlPortTemplate or OtherMemoryPortTemplate. In        all cases, each DataPort in an IDTag will point to the proper        template for that data port.

The DataPortTemplate tells how many (32-bit unsigned) words are in thedata port, if the length is fixed (WordCount). In addition, if the portcan have a variable length, the DataPortTemplate indicates this withIsVariableLength; in such a case, the DataPort itself tells the currentnumber of words in CurrentWordCount (for some tags this is fixed, forothers it can be adjusted by the reader).

Some data ports have fixed characteristics; others can vary from tag totag. If the characteristics are variable, the reader may have tointeract with the tag to determine the characteristics of each dataport. The IsDescribed property in the DataPort tells whether the otherproperties are all known to be valid. If this is false, then theremaining fields may require interaction with the tag before they can beread or written to by the application.

The data port can be read from the physical tag if indicated by theDataPortDescription. If the data port is word-addressable, then thereader will allow ranges of words to be read. The contents of a readableport may be cached in the IDTag model if permitted by the IsCacheableBoolean in the DataPortTemplate; if not permitted, then the value of thedata port may vary over time, so an application should not cache thevalue. (An example would be a data port that corresponds to a sensorinput measurement or an available data file.) The DataPortTemplateindicates whether the data port can be read-locked (i.e. set to a statethat prohibits reading).

The data port can be written to if indicated by the DataPortTemplate. Ifthe data port is word-addressable, then the reader will allow ranges ofwords to be written. The DataPortTemplate indicates whether the dataport can be write-locked (set to a state that prohibits writing). ASecurity Key Set may accompany the DataPort, if so indicated in theDataPortTemplate.

Tag-Initiated Reports

Some tags can initiate a transaction with a reader, depending on eventson the tag (such as sensor readings, activation of a UI device such as abutton, or receipt of external signal such as a proximity beacon). TheIDTagTemplate lists such events for a given type of tag, giving a nameand description string for each type of event a tag can report.

At this time, the reader's handling of such events is consideredhardware-dependent and the data that would accompany such an event isnot standardized at all. It is expected that some kind of data objectwould accompany the report of a tag-initiated event, to describe thedetails of the event as reported by the tag or determined by the reader.

Design of the Security Key Classes

It is impossible to predict all variations of security algorithms andkeys that may be used with IDTags. Therefore, a simple and general modelis used for security.

Security is provided by “key sets”—one for the tag, and one for eachdata port. These represent the program's knowledge about the keysrequired to interact with the tag. The IDTagTemplate will indicate whatkeysets and keys are used through the attached SecurityKeySetTemplates.

Each key set consists of an (unordered) array of zero or more keys. Eachkey has a name and description, and an associated value (represented asa binary array or string using WordString). In the SecurityKeyTemplate,the name is given, along with a WordStringTemplate and an optionaldefault value. There are also bits to indicate whether this key can bewritten to the tag, and whether it can be write-locked. In theSecurityKey itself, there is a value and (if appropriate) a bitindicating whether this key is write-locked.

In use, when a new ID is discovered, a corresponding IDTag object shouldbe created, and the necessary security keys attached. Whenever the IDTagis passed to a reader operation, the security keys will be available tothat operation. The operation can search the key sets in the IDTag todiscover the keys it requires (which will be listed in theIDTagTemplate), and utilize the associated values to carry out its task.

For example, a particular type of tag might allow a 96-bit password tobe associated with each tag for data encryption. It might be called the“Encryption” key in the tag's key set. The IDTagTemplate would indicatethis by an entry named “Encryption” in the TagKeySetTemplate property;this entry would have a WordStringTemplate indicating ExpectedLengthequal to 3 (3×32 bits=96 bits). When a new tag is encountered, itsencryption password should be looked up according to the enterprise'skey management facility, and that value should be placed in a key called“Encryption” in the TagKeySet of the new IDTag. When the IDTag instanceis passed to a reader method, the method will search the TagKeySet for akey called “Encryption”, and use the associated value in theencryption/decryption algorithm as it communicates with the tag.

Accordingly, in at least one aspect of the invention, possiblyimplemented in software, information is communicated between a readerdevice and an application in a tagging system by transmitting a scaninstruction to a reader regarding one or more tags, retrieving atemplate associated with each tag scanned, and transmitting a taginformation report to an application, the report including the templateassociated with each tag scanned so that the application can identifyand manipulate elements of tags of differing tag technologies. Thetemplate can describe a type of tag scanned, and/or the report caninclude an object model of the tag having components descriptive ofcharacteristics of the tag, and including the template associated witheach tag scanned or including a pointer to a location of the templateassociated with each tag scanned so that the application can identifyand manipulate elements of tags of differing tag technologies.

In other aspects, each template can have a name including a bit stringthat associates a respective tag type with the template. Or, a templatecan exist for each type of tag, the template including information abouta configuration of each type of tag so that the application caneffectively take advantage of features of a respective type of tag.These features provide that the application need only receive arespective template once, the application then being capable ofinterpreting all subsequent reports directed to a type of tag associatedwith the respective template.

Another embodiment of the invention includes a data structure having anactual identification field, a temporary identification field, one ormore memory fields and at least one security key field, the datastructure enabling an application to process various kinds of ID tagtechnologies. The data structure could further include one or moreDataPort fields of either a ControlPort type or a MemoryPort type.

The actual identification field could be binary or a character string,where the actual identification field being viewable as a characterstring in either case. The actual identification field could be asubclass of WordString that adds a Name string and a Description string.Further, the data structure and each component of the data structurecould include a link to a corresponding template.

If the actual identification field of the data structure has differentcorresponding actual identification field templates, then the respectiveactual identification field templates can be ordered according to a Nameproperty of the actual identification field templates. Or, if the actualidentification field of the data structure is the same as correspondingactual identification field templates, but are variable length withdiffering lengths, a shorter actual identification field template can befirst in order.

Memory fields provide the capability of storing all data necessary todescribe an ID tag but an initial scan of the ID tag only populates asubset of the memory fields due to pre-determined scanning timeefficiencies. The memory fields unpopulated by the initial scan can bepopulated upon later request by an application for additional data.

IID TagReporter Interface

This section presents uses and design for an IIDTagReporter interfacefor middleware, forming a portion of the present invention, thatprocesses ID-bearing labels or tags from a variety of AutoIDtechnologies including bar codes, magnetic stripe cards, SmartCards,RFID tags, 802.11 badges, etc.

While various AutoID technologies differ in many respects, from a dataprocessing standpoint they have a great deal in common. A primaryoperation of all AutoID technologies is to generate a list of all tagsin view of a reader, along with their IDs; other operations involvereading, writing, and/or control functions applied to specificidentified tags in view of the reader. In application settings, thedifferent AutoID technologies can sometimes be merged into a single datachannel, and processed by a single middleware component.

The IIDTagReporter interface can represent the reader devices from allsuch AutoID technologies in a single abstraction, suitable for theconstruction of such technology-agnostic middleware. The presentinvention captures key features of the scanning of IDs, and provides ageneric transport mechanism for implementing more specific functions byapplying read, write, and control functions.

Design of IID TagReporter Interface

For Windows Longhorn, the preferred way to define classes is throughabstract class definitions rather than interfaces. A key reason is theease of extension and upgrading by extension. However, MSDN lays outspecific criteria under which it may be preferable or necessary todefine an interface. One reason is diversity of underlying providers.Another is the need for multiple inheritance, as when implementingcomponents within a framework that has other constraints.

This criteria applies to the tag reporter interface of the presentinvention. Underlying providers, as described above in the use cases,can be anything from a device to a networked software service. And, insome cases, there are external constraints that a provider must satisfy.For instance, in Chinook, inheritance must be from the Chinook genericservice object class. These reasons provide a basis for providing aninterface, rather than an abstract class, in the present invention.

Operations supported between ID tags and tag readers are:

-   -   Scan—The reader makes a list of the ID tags it can sense. This        is actually a comprehensive activity with many possible        subparts.    -   Read/Write DataPort—The reader sends data to a tag and/or        receives data back.    -   Write ID—The reader changes the stored ID value on a tag.    -   Control Tag—The reader tells a tag to do something.    -   Lock/Unlock Data—The reader sets or removes a read lock or write        lock on a tag element.    -   Describe Tag—The reader interacts with a tag to determine its        characteristics.    -   Receive Tag Events—The reader receives an unsolicited        transmission from a tag.    -   Deactivate Tag—The tag will no longer respond to readers        Issues and variations on these operations are described below.        Design Issues—ID, IDTag, and IDTagDictionary

An ID object model is used to represent a single ID from a single tag.The ID can be in binary or character-string format, and can befixed-length or variable-length. The IDTag object model represents asingle tag.

An IDTagDictionary can be thought of as a hash-table using IDs as thekeys and IDTags as the corresponding values. However, it is specializedto recognize that if two IDs come from different series (e.g. differentmanufacturers) they are distinct, even if they have the same ID value.The chief use of an IDTagDictionary is to use an ID to look up thecorresponding IDTag object instance.

If an application wants to store information related to specific tags, aPrivateDictionary is preferably used, supplying the ID fields of thetags as the keys and any desired objects as the values. If IDTags areprovided as keys, their ID fields can be used as the underlying keys inthe PrivateDictionary. Thus, a PrivateDictionary associates IDs (orIDTags) with arbitrary objects.

An IIDTagReporter provides access to both an IDTagDictionary and anIDTagReportDictionary. The IDTagDictionary can be used to look up anIDTag given an ID, whereas the IDTagReportDictionary is used to look upthe latest (current) tag status given either the ID or IDTag.

Scanning Model

Referring to FIG. 7, a fundamental Scanning Activity has any or all ofthe following elements (where outline numbering corresponds to Figurenumbering):

-   -   1. An initiator 1 action occurs.    -   2. The reader initiates one or more scans of the tags in its        vicinity using one or more collectors 2 a attached to sensors 2        c that feed into the reader, accumulating the results into a        list. The scans may be filtered 2 b/d so that only a subset of        the tag responses are included.    -   3. If the reader has any attachments 3, they may be activated.    -   4. Any of several housekeeping activities 4 may then take place.    -   5. A report list is generated and returned via a report event 5.

1. Initiators: A scan can be initiated in response to a number ofdifferent occurrences, including:

-   -   Immediate operation.    -   Timer interval.    -   Particular time on the clock.    -   * External signal on a specified port and pin.    -   * External value supplied to a specified port.    -   * Reader-specific occurrence.    -   * Tag-specific occurrence (possible with certain types of tag).

The initiators marked with * are considered to be defined by thedeployment configuration of the reader (see below); the others areinherently defined for all readers.

2 a. Collectors: A collector might be, for example, a particular antennaattached to a multi-antenna RFID device. For most readers, there is asingle collector.

2 b. Scan Filters (hardware): In some technologies, a filter can bebroadcast to the tags in the vicinity of the reader before a scan; then,only the tags that match the filter will respond to the scan. Matchcriteria might include a boolean combination of primitives; for example:(1) ID or memory contents within a specified range; or (2) ID or memorycontents in which specified bits match a specified pattern. Clearly,most tag varieties will support a very limited subset of these criteria.Note that if tags use Alias IDs (see below), the ability to filter basedon ID may be quite limited; also, if tags encrypt their data, thenfiltering might require that an appropriate key be supplied to the tag.

2 c. Sensors: Some readers have more than one sensor. In a scan activitydescription, a sequence of collector/sensor pairs can be specified,along with an indicator of whether it is desired that these combinationsbe invoked sequentially or simultaneously. Most readers will be able toimplement a very limited subset of this full capability.

2 d. Scan Filters (software): If a reader cannot implement scan filtersin hardware, it is likely that a full scan will be performed and desiredtags selected through application of the indicated filter in software. Areader with a limited hardware filter capability could actuallyimplement more comprehensive filters using a combination of hardware andsoftware filtering.

3. Attachments: Some readers may have external devices that can beactivated, such as making a beep when a scan occurs. Such attachmentscan be specified as part of a scan activity.

4. Housekeeping Activities: The reader may be asked to perform any orall of several tasks before generating a report. These tasks include:

a. Alias ID Resolution. In some technologies, tags do not return theirreal IDs to a scan command. Instead, they generate a new random number,called an Alias ID, or temporary identification, for each scan. Forthose technologies that have a real ID as well, the reader can “resolve”the alias ID to a real ID by sending security keys (such as an unlockingpassword and encryption key) to the tag in order to receive back thereal ID. In a scan activity, the reader may be instructed to performAlias ID resolution automatically for every Alias ID received. (Note 1:In some technologies, automatic resolution is always required, and thereader must store the correspondences between real and alias IDs forlater use.) (Note 2: If automatic resolution is not performed, thetags's real IDs are not known until the application has received the tagreport and made specific request for the reader to resolve specificalias IDs.) Generally, applications will want to specify automatic AliasID resolution in the scan activity. Alias ID resolution is described inmore detail below.

b. IDTag Lookup. In most cases, the application will not want the IDreturned directly; instead, the reader should keep an IDDictionary ofIDTag objects, and look up the IDTag for each ID that is scanned. Thislookup will generally be required if Authentication and/or Descriptionare specified (see following paragraphs). The reader will need to keepan internal IDDictionary for this purpose. Filters may choose to use thesame IDDictionary as their underlying providers; for this reason, eachIIDTagReporter object also implements the IIDDictionary interface toexpose its internal IDDictionary. If automatic lookup is not specifiedin the scan activity, then the reader must create a new IDTag object foreach ID it scans, in order to generate the subsequent report. Note thatif Alias IDs are supplied by a tag, but automatic resolution is notspecified, then IDTag lookup is impossible and the reader must create anew IDTag object for each Alias ID it receives during the scan.

c. Authentication of Tag ID. Some tags may provide anti-counterfeitingcapability by implementing some kind of authentication. Usually, thisrequires some algorithmic interaction with the reader involving one ormore security keys on the reader as well as keys stored on the tag, andpossibly some other criteria that are hard to duplicate (such as minutevariations in the structure of the radio antenna on an RFID tag, orminute variations in the filter arrangement of a bar code label).Authentication may be required by the scan activity description; tagsthat fail should generate an exception, and their IDs should beconsidered unreliable. An authenticating reader is specialized; not allreaders will have this capability.

d. Tag Description. As previously described, scanned tags may haveconfiguration parameters that are unknown until further reader/taginteraction takes place. This interaction is called Description in theIDTag SDK. An application is not permitted to access fields of the IDTagobject other than the ID itself, until the tag is described and assertsthe IsDescribed property. An application can indicate in the scanactivity specification that all tags scanned are to be fully describedbefore the tag report is generated. (If IDTag Lookup is also specifiedabove, then a tag need only be described the first time it is scanned.)Note that each memory port may similarly require tag interaction todiscover a complete description—if automatic description is specified inthe scan activity, then it includes description of the tag as well asdescription of each memory port, before the report is generated.

e. Checktag Recognition. “Checktags” are specific tags used for specificpurposes, primarily: (1) to signal to a reader to enter a diagnosticmode; (2) to signal a mobile reader that it is at a specific location;or (3) to be scanned always by an antenna, so that its absence from ascan indicates a hardware malfunction. As part of a scan activity,checktags may be specified; if a checktag is discovered in the scan (ornot discovered, as indicated), then a separate report is generated via adistinctive reader event (OnCheckTagReportEvent rather thanOnReportEvent).

5. Report Generation: A TagReport is generated for each tag IDdiscovered in the scan, and these are collected into a TagReport,described further below. The TagReport is returned via an OnReportEventevent.

A Scanning Activity may also specify that after each scan, scanning isto be suspended, SuspendScanning( ). If specified, then theapplication's OnReportHandler should issue ResumeScanning( ) to tell thereader to resume scanning activities. This can be useful, for example,when Alias IDs are in use, and tag I/O may be required before the nextscan is initiated (at which point all the Alias IDs would be randomizedagain).

Specification of Scan Activities. A ScanActivity object specifies a scanactivity, including all of the parameters needed to control andimplement elements 1-5, above. Each ScanActivity has a name, which ispreferably inserted in the Originator property of each IDTagReport.

When a scan is performed, an array of ScanActivity objects is provided.The reader shall then perform all of these activities simultaneously.(Most readers can only implement one activity at a time, but some mightbe able to have several initiators active, with a distinct ScanActivityfor each initiator). If Scan( ) is invoked without a list, the reader'sDefaultScanActivity property supplies the list of scan activities toperform.

Regardless of the source of the list of scan activities, a copy of thatlist will be placed into the reader's CurrentScanActivity property bythe Scan( ) method. A Scan( ) method call with an empty list (array of 0elements) instructs the reader to stop scanning and clears the currentscan activity specification. This is different from the SuspendScanning() and ResumeScanning( ) methods, which cause a temporary halt but do notchange the scan activity specification.

Regarding item 4 a in further detail, Alias IDs and Alias ID Resolution,note that the Alias ID mechanism was incorporated by EPC Global into newGEN2 tags. Alias ID changes the way a reader interacts with a tag, andalso changes the way a server interacts with the reader.

Alias ID provides that a tag may have a password that is required from areader before the tag will reveal information to that reader. This,however, creates a problem: how does a reader know that there is a tagin its vicinity, since the tag will not provide information until itreceives a password? The resolution is that every time a reader requestsa scan or tag response, each tag generates a random number (the Alias IDor temporary identification). The random number becomes a pseudonym forthe tag for use until the next scan, at which time the tag generates anew random number. Therefore, the Alias ID is a temporary, or limitedlifetime, name. During this interval or lifetime, the reader may addressthe tag by the Alias ID, present credentials in the form of thepassword, and request that the tag begin further communication,including revealing its true ID number, or permanent identification,along with other information.

Accordingly, Alias IDs provide privacy and security, by preventing anoffering of information to any reader request. With Alias ID, a readermust offer a password to the tag before receiving the desiredinformation.

Without Alias IDs, the basic duty cycle of a reader would be, forinstance, to perform a tag scan, receive responses, includingidentification numbers, effectively serialized through anti-collisionmechanisms, report the responses to a respective application, and scanagain. If a specific read/write request was desired for an individualtag, the system would wait until the scan is complete, and uponreceiving such notice, software would instruct the reader to perform thespecific operation prior to performing the next scan.

With Alias ID a more complicated protocol is needed because what thereader receives from the tags is a set of random numbers not applicableto the performance of business functions. For applicability, each AliasID, or temporary ID, must be resolved to the actual or permanent ID ofthe corresponding tag, which are meaningful to the application. Thatprotocol is referred herein to Alias ID Resolution. In short, a readeraddresses a specific tag using its Alias ID, presents its credentials,asks for the actual ID, and receives the actual ID.

The present invention provides the following mechanisms forincorporating Alias ID Resolution into software for applicationcommunication with the reader. First, software can request that areader, every time it performs a scan, perform resolution on every aliasID received prior to returning a report to the application, referred toherein as “Resolve On Scan.” Accordingly, the reader will perform ascan, receive Alias IDs, perform resolution on each, in turn, and, onlywhen all resolutions are complete, send a report to the applicationwhich may or may not trigger business activity in the application. Thereader is then free to perform another scan. Second, where time is ofthe essence, or where the application has an external way of knowingwhich tags are interesting and desirable, the application can instructthe reader, through the IIDTagReporter Interface of the presentinvention, not to perform Alias ID resolution on every tag, but rathercreate a temporary tag object for each Alias ID received by the reader.Temporary tag objects could then be reported to the application. Theapplication can then request Alias ID resolution on only those tags ofinterest. This mechanism is referred to herein as “Resolve On Demand.”

Also, the Suspend Scanning aspect of the present invention correspondsto Alias ID resolution. The application may instruct the reader that,after it performs a scan, and associated steps 1 through 5, the readerwill suspend operation and not immediately issue a new scan untilreceiving a specific instruction from the application. This prevents anundesirable regeneration of new Alias IDs, at which time it may beimpossible for the reader to implement a subsequent instruction by theapplication to read, write or control a specific tag. With SuspendScanning, the application can instruct the reader to pause, providingthe application time to determine whether further tag interaction isdesirable before a new scan resets all of the Alias IDs to new values.

Accordingly, in at least one aspect of the invention, possiblyimplemented in software, tag identifications are resolved by performinga scan of one or more tags, receiving temporary identificationinformation for each of the tags, selectively ordering the temporaryidentification information, and resolving the temporary identificationinformation to permanent identification information for each tag in theorder selected prior to performing another scan. Or, after receiving thetemporary identification, a temporary tag object could be created foreach temporary identification information received, the temporary tagobjects could be reported, a request could then be received forresolution of one or more temporary tag objects in a selected order, andthe temporary tag objects would then be resolved to permanentidentification information for each tag in the selected order.

This activity could be entirely performed prior to performing anotherscan. The temporary identification information could be a randomcharacter string. A further scan could then occur, perhaps upon receiptof instructions from an application, and temporary identificationinformation for each tag would be reset and re-populated with a randomcharacter string. Or, during the process above, an instruction could bereceived to suspend further scanning pending further instruction,allowing interaction with the one or more tags prior to a resetting ofthe temporary identification information upon a further scan.

Other aspects of the invention, possibly implemented in software,include managing ID tag scanning and reporting by initiating a scan ofone or more tags, instructing a collection of ID signals transmitted asa result of information gathered during the scan, the ID signalsincluding a tag identifier for each tag, and generating and forwarding ascan report to an application. Any one or more of the followingactivities could also be performed, either prior to, during, or aftergenerating the scan report:

-   -   where the tag identifier is a temporary tag identifier,        resolving the temporary tag identifier for each tag to a        permanent tag identifier;    -   looking up an actual object model for each tag using the tag        identifier;    -   authenticating each tag;    -   gathering and storing all descriptive information available for        each tag; and    -   recognizing any checktags and generating an associated alert;        and    -   generating and forwarding a scan report to an application.

Resolving the temporary tag identifier to a permanent tag identifiercould be required before performance of any subsequent step. Thisresolution could involve the forwarding of a security key to therespective tag to receive the permanent tag identifier. Looking up theactual object model for each tag using the tag identifier could beperformed in the application or the reader.

Checktags can be a list of one or more tag identifications generated bythe application and forwarded to a reader with instruction that if anyof the tag identifications are (or are not) recognized during a scan aspecial alert is to be forwarded to the application and the respectivetag identification is, or is not, to be included in the scan report tothe application. At any time in the process, a suspension of furtherscanning instruction could be implemented, allowing interaction with oneor more tags prior to a resetting of temporary identificationinformation upon the next scan. Trigger conditions could be set toinitiate any one or all of the scan activities.

Another aspect of the invention is a data structure having one or morequality-of-service fields describing importance parameters to a tagreader of a quality of pre-determined activities relative to speed ofcompletion of the activity. The parameters could govern any one or moreof:

-   -   elimination of false negatives (missed tags) in scan operations;    -   elimination of false positives (ghosts) in scan operations;    -   confidence that read operations have succeeded;    -   confidence that write operations have succeeded;    -   confidence that a tag is authentic (not counterfeit);    -   maximum packing of data into an available user-memory on a tag;    -   maximum range for communicating with tags;    -   number of tags in communication range of a tag reader; and    -   precision of location information of a tag.        Lastly, the importance parameters could have values such as less        important than speed, as important as speed, more important than        speed and most critical.        Reports: IDTagReportList

A report generated by a scan is an IDTagReportList object.IDTagReportLists are designed to run fast for sequential processing, asin this scenario:

-   -   A. A component (such as a filter) maintains an ArrayList of all        the IDTags it believes to be in range of the reader. This list        is sorted by increasing ID.    -   B. A scan is performed, and the reader returns a new        IDTagReportList of the tags just scanned. When this list is        received, it is then sorted by increasing ID value (if not        already sorted).    -   C. Now the ArrayList and the IDTagReportList are compared in        order of increasing ID, while creating a new ArrayList of tags        believed to be in view of the reader. Newly arrived tags are        easily noted, as well as departing tags (known tags that were        not included in the IDTagReportList) and tags seen again        (present in both the ArrayList and the IDTagReportList).

Each IDTagReport has the following properties:

-   -   IDTag object    -   Timestamp (the time at the start of the scan)    -   Condition (the type of entry being reported, such as “observed”        or “departed”)    -   Originator or the entry (typically the name property of the        ScanActivity)    -   Location associated with the entry (if any)    -   Extra, reader-specific “associated data”

It may be preferable for an application to know which, if any, of theproperties listed above are the same for all entries in the IDTagReport.For example, a filter might be written with the assumption that a singlereport contains all entries from a single originator and timestamp. Forthis reason, as entries are recorded into the IDTagReport, they areexamined to see if they all have the same value for each property. Ifso, the common value of the property is made available in theIDTagReport object itself, so that the application can assume that allentries have the same value for this property. If the IDTagReport isserialized, it will be unnecessary to include these repetitive propertyvalues for each entry.

Location and Source Determination

Tag reports of the present invention include separate fields forlocation and source, integrating all sources of location through RFID.

The present invention contemplates at least seven approaches forderiving location information from a tag reading, and each areincorporated into the object model herein. The hardware technologiesinvolved with the approaches are quite different, and the software maydiffer depending on whether or not servers are involved, etc. However,in the IIDTagReporter interface, all are unified into one object model.Accordingly, the present invention provides that software applicationscan be written that use location information regardless of whichapproach is used by the hardware to derive the location information.

Referring to FIG. 8, a first approach assigns a name, or ID, to eachreader. The ID or name of the reader is used as the location. Forexample, reader number #1234 may be assigned to a dock door, which isreferred to as dock door A. Reader number #1234 could be used as alocation. Accordingly, receiving a tag reading stating that the tag camefrom reader #1234 would reflect a different location than a report froma tag stating that it came from reader #5678. A variation would be toassign a name the antenna. Another variation to this approach is toassign place names, like dock door A, dock door B, dock door C, andproviding a means to translate from the reader or antenna ID# the nameof the place to which that reader or antenna is located. The businesslogic in the application could be based on either the reader ID# or theplace name, but probably more convenient to use the place name in thebusiness software, since it is one level removed from the actual readerID#. Either way, this is the most common approach used today, and theapproach included in the specification for EPCglobal, where it isspecified that tag reports have one field, referred to as “sort,”indicating where the report came from. The present invention providestwo fields. One field is for source, that is, where the reportoriginated, meaning the device or device component that originated thereport. The second field for location, corresponding to where the tag isbelieved to be. In simple systems, both fields may have the same value.However, separate fields with different values provide advantages inmany technologies.

Referring to FIG. 9, a second approach uses location checktags, asdescribed above. In this approach, a reader, when reading a tag,associates that tag, or tag ID#, with a given location, using the tag'sID#, or associated data retrieved using the tag ID, as the identity ofthe location. In this approach, the source of the reading is actuallythe reader, but the location is the location at which that tag exists.In this approach, the source and the location fields would be different.This approach is primarily directed to mobile readers.

Referring to FIG. 10, a third approach adopts Trilateration, wheremultiple readers or antennas read a given tag at the same time, or in away that is synchronized over time. And each of the multiple readersindependently determines how far away the tag is from the respectivereader. This distance could be in absolute terms or in relative terms,relative to some arbitrary scale or to a scale in conjunction with theother readers. The location of the tag could thereby be determined inthe space spanned by the receiving zones of all the readers. There maybe calculations performed externally, or performed on a reader, or on aserver, where raw measurement data from the readers is turned into alocation determination. In the example illustrated in FIG. 10, thesource of the data would be the server and not any specific device.

Two implementations of Trilateration are time of flight and signalstrength. Time of flight is the difference between the times of signaltravel from each of the multiple antennas. Time techniques involvedetermining a time synchronization across the readers, which can bedifficult to establish. Signal strength methods are affected not only bydistance, but also by any intervening objects or materials through whichthe signal must pass.

Referring to FIG. 11, a fourth approach is Signal Strength Signature,where signal strength is measured by several readers, and a look upprocess is implemented rather than a calculation process. With SignalStrength Signature, each reader does attempt to determine how far awaythe tag is, rather a signal strength is provided with each tag observed.The look up is established through a survey performed in the field,determining and recording signal strengths at different locations, thenstoring the signal strengths in a table for look up as needed.

Referring to FIG. 12, a fifth approach incorporates another hardwareelement, called a beacon. Beacons typically broadcast an ID# over ashort range, and are usually inexpensive. In this approach, a beacon ispositioned at any location of interest. When a tag enters the zone ofthe beacon, the tag receives a broadcast including the beacon ID#. Thetag then reports the beacon ID#, and its own ID#, over a longer range ofcommunication to a central antenna. That information can be is stored ina server for later look up, and can be reported to the application.

Referring to FIG. 13, a sixth approach implements tags with locationsensors, where a tag may be used for telemetry, and RFID is a carrier ofsensor data ID# to a reader and application.

Referring to FIG. 14, a seventh approach uses a specialized antenna, orcollection of antennas, to implement differential times of flighttechniques to record the minute differences in the time of arrival atthe various antennas, thereby determining the location of the tag.

Table 1 provides a summary of the approaches, what each reports, andwhat assumptions are made about the tags and the readers. TABLE 1Summary of Techniques Tag Reader Location Reader ID Any Any Reader IDTag ID Any Any Tag ID Trilateration Active Special x-y-z SignatureActive Special Spot ID Beacon Special Special Beacon ID Sensor SensorSpecial Any, e.g. x-y-z Ph. Array Any Any * x-y-z

The present invention unifies all seven approaches by separating asource field from a location field. “Source” indicates how to contact atag for further interaction; and “Location” informs where the tag isusing universal location schema. Table 2 illustrates information placedinto a source field and a location field to accommodate each of theapproaches. TABLE 2 Location Reporting in IDTag SDK Source LocationReader ID Reader ID Reader Location Tag ID Tag ID Tag LocationTrilateration Calculation Server Calculated x-y-z Signature LookupServer Spot Location Beacon Lookup Server Beacon Location Sensor ReaderID Reported Location Ph. Array Reader ID Calculated x-y-z

Note that Location could be indicated universally across the differentapproaches, requiring a unique location description. An example isMicrosoft's WinFS, where Location is a collection of LocationElements,subclassed as coordinates (+uncertainty+coordinate system); entity ID(+database+database type)(including the case of a list of names used aslocations); street/postal address; and electronic endpoint (IP address,etc.). LocationReport, as part of WinFS also has metadata about thesource, time, etc.

Accordingly, in at least one aspect of the invention, possiblyimplemented in software, tag location information is derived from a tagreading by performing a scan of one or more tags, and generating a tagidentifier for each tag scanned, the tag identifier including a sourcefield and a location field so that location can be derived regardless ofa tag location technology employed.

The source field can provide information pertinent to contacting eachtag for further interaction and/or identify a hardware component fromwhich delivery of the respective tag identifier originated. Examples ofthe hardware component could be Reader ID, Tag ID, a Calculation Server,or a Lookup Server.

The location field could identify respective tag locations usinguniversal location schema and/or could identify where the respective tagis physically located. The physical location of the respective tag couldbe identified by Reader location, Tag Location, Calculated x-y-z, SpotLocation, Beacon Location, or Reported Location. Moreover, the sourcefield and the location field include identical values. The Tag locationtechnology employed could be Reader ID, Tag ID, Trilateration,Signature, Beacon, Sensor or Phased-Array, among others.

Another aspect of the invention is a data structure for deriving taglocation information from a tag reading, and includes a tag identifierincluding a source field and a location field, providing that locationcan be derived regardless of a tag location technology employed duringthe tag reading. The source field and location field retaininginformation as articulated above.

Description and Deployment of the Reader

The properties of the reader are broken into two parts, reflecting thefundamental hardware, and the way the hardware may be set up for use(“deployment”).

The hardware is described in a ReporterDescription object.ReporterDescription includes:

-   -   Name and Description of the reader    -   Version (a string that should encode the version information for        hardware, firmware, and software)    -   A list of the names of the communication protocols that the        hardware can implement    -   A list of the TagTemplates for the tags that the reader can        recognize, where a filter inherits the TagTemplate list from an        underlying provider.    -   An indication of the features the reader supports    -   Pass-thrus for reader properties, methods, and alerts

Distinct from the hardware is the way that a reader may be configured,which can depend on how it is intended to be used. This is described ina ReaderDeployment object (the reader's current configuration isrecorded in its CurrentDeployment property). ReaderDeployment includes:

-   -   A list of which types of initiator the reader can support    -   A description of the initiator ports on the reader    -   The set of deployment initiators available in the current        configuration (ports with pin signals, ports that supply values,        provider-specific initiators, and tag-generated initiatiators)    -   Lists of the collectors, sensors, and attachments available for        scan activities.    -   A list of the possible condition names that the reader can        report.

In an enterprise setting, the deployment configuration of the readerwould be obtained from some stored configuration specification (such asa file containing a serialized ReaderDeployment object).

Reader Protocols and Tag Descriptions

Some readers may support multiple radio protocols, either one at a timeor in certain allowed combinations. Similarly, some readers may becapable of recognizing several types of tags.

Specifying all of the hardware characteristics implied by each protocolis not possible. Therefore, in IIDTagReporter, each protocol is simplydenoted by a character string that may be meaningful to the reader.

Each type of tag is described in an IDTagDescription object, asdescribed under IDTag Object Model, above. It is expected that a readermight, for example, read XML files for all of its attendant tag typeswhen it begins operation. Each IDTagDescription lists one or moreprotocols under which that type of tags can be recognized.

A caller can ask an IIDTagReporter to give a list of all supportedprotocols, or all supported tag types. The caller can specify a set ofprotocols the IIDTagReporter should enable itself to simultaneouslyutilize (if possible), and the caller can ask what set of tag types canbe recognized with the current set of enabled protocols.

Other Reader Properties and Methods

The IIDTagReporter interface can also include:

-   -   An exception event handler    -   Pass-thrus for reader-specific properties, methods, and events

IIDTagReporters can perform the following tag interaction operations:

-   -   Write and/or write-lock the ID field    -   Resolve an Alias ID (if not resolved automatically in the scan        activity)    -   Obtain a complete description of the tag    -   Deactivate the tag    -   Obtain a complete description of a data port    -   Read a data port or part of a data port (if word-addressable)    -   Write to a data port or part of a data port (if        word-addressable)    -   Write-lock a data port or part of a data port (if        word-addressable)    -   Set security keys for the tag or for a specific data port    -   Perform a tag-specific operation

IIDTagReporters can also implement the following functions:

-   -   Verify that the reader can perform a candidate set of scan        activities    -   Verify that a candidate tag-specific operation can be carried        out    -   Restore the factory settings to the reader    -   Reboot the reader    -   Suspend, Resume, and Clear operations (see Asynchronous        Operation below)        Asynchronous Operation

In general, IIDTagReporters support both synchronous and asynchronousoperation. Scanning is inherently asynchronous; and is therefore not thefocus of this section.

The methods of IIDTagReporter (other than Scan) are preferably writtenin synchronous form—a call on a method will block until the action iscompleted and a value can be returned if appropriate.

For asynchronous operation, the standard pattern can be used. Insummary, the caller creates a delegate whose signature matches thedesired method; assigns the method to that delegate; then executes theBeginInvoke method that Visual Studio automatically defines for everydelegate. BeginInvoke creates a new thread to execute the method. Theoriginal thread returns immediately to the caller and provides anAsyncResult object; the new thread executes the method in a synchronousway (blocking to wait for I/O activities). The original thread can pollthe AsyncResult object or block until it completes (using WaitOne); thenEndInvoke can be used to retrieve the result returned by the method.

If a caller invokes several asynchronous operations, the new threadswill chase each other down the stack of filters. Therefore, allimplementations of IIDTagReporter are required to be thread-safe. If anIIDTagReporter covers a single-use device (such as a network client or aphysical sensor), then all incoming method calls should be madesequential using normal means (such as a Monitor on a lock object; seenumerous MSDN articles on the subject).

IIDTagReporter also specifies the operations of SuspendAllOperations( ),ResumeAllOperations( ), and ClearPendingOperations( ); these can beimplemented as follows:

-   -   SuspendAllOperations( )—when the current operation (if any) is        finished, the governing Monitor should not be released        automatically. This might require an additional Monitor lock        object for implementation. Also, scan activities should not be        initiated.    -   ResumeAllOperations( )—the current operation (if any) can        release the governing Monitor normally. Scanning activities may        be initiated again.    -   ClearPendingOperations( )—all operations that are waiting for        the locked Monitor should be cancelled and should immediately        return indicating failure due to cancellation. Implementing this        probably requires an additional locked “cancel” boolean.        Security Model

A single specific security model for all ID tag technologies is notfeasible. Instead, the present invention provides “security keys”including a name and value, which can be collected into sets. The keysfor tags are maintained in the IDTag model; where a method is providedto write and/or write-lock security keys on the tag.

The IIDTagReporter is equipped with a set of keys to use in carrying outits functions. In addition, a set of “default tag keys” isspecified—these keys can be passed on to newly created IDTag objectsduring a scan activity. The use of all these keys is hardware-specific.

QOS Tuning Model

IIDTagReporter provides a simplified model for tuning thequality-of-service parameters of the provider. The present inventionprovides a number of parameters, and each can be traded off againstspeed. The parameters govern:

-   -   Elimination of false negatives (missed tags) in scan operations.    -   Elimination of false positives (ghosts) in scan operations.    -   Confidence that read operations have succeeded.    -   Confidence that write operations have succeeded.    -   Confidence that a tag is authentic (not counterfeit).    -   Maximum packing of data into the available user-memory on the        tag.    -   Maximum range for communicating with tags.    -   Number of tags in communication range.    -   Precision of location information

Each parameter has one of the following values: LessImportantThanSpeed,AsImportantAsSpeed, MoreImportantThanSpeed, MostCritical. Only oneparameter can have the value “MostCritical” at any time; if there is aMostCritical parameter and a different one is set to MostCritical, thenthe first is degraded to MoreImportantThanSpeed. The default value ofall parameters is LessImportantThanSpeed.

The interpretation of these parameters is entirely up to the provider.For example, the default Write operation might try a single write; ifAsImportantAsSpeed, then it might write and then verify; ifMoreImportantThanSpeed, it might try several cycles of write-and-verify;and if MostCritical, it might try many cycles before reporting failure.

The IIDTagReportFilter Interface

A report filter is an object class that calls one or more IIDTagReporterobjects as underlying providers, and in turn exposes theIIDTagReportFilter interface (i.e. is a provider forIIDTagReportFilter). IIDTagReportFilter extends IIDTagReporter, whichmeans that a filter can in turn be used as a provider to anotherhigher-level filter or application.

IIDTagReportFilter uses an array of IIDTagReporter objects to keep trackof the topmost implementor for each property, method, and event in theinterface. This is used to implement drop-thrus for elements that arenot implemented in the current IIDTagReportFilter. In the constructor, afilter should make a copy of its provider's list; and set all theentries that correspond to elements implemented in this filter to“this”.

If an IIDTagReportFilter contains an internal IDTagDictionary and/orIDTagReportDictionary, then they are exposed to the caller. However, ifit does not, then it exposes the IDTagDictionary andIDTagReportDictionary of its underlying provider.

Virtual Reader Design (Filters)

FIG. 15 illustrates an Overall System Model, and indicates that manyentities, each defining parts of a software system, can affect themiddleware. In most systems, there are different models for the entitiesto inject their elements into a final system design. In the IDTag SDKthere is a mechanism to incorporate constraints of the differentsources, referred to herein as filters, or programming devices.

FIG. 16 illustrates an interface between a provider of ID reports and aconsumer of the ID reports. Previously, this specification referred to areader and an application. Throughout this section the description mayreference a provider and a consumer, because there can be many providersand consumers in a system. The IIDTagReporter is the interface throughwhich they speak. Elements included and managed in the interface are: 1)configuration parameters that go from consumer to provider; 2) a set ofscanning activities that a consumer forwards to a provider; 3) providerreports forwarded to a consumer including observations of tags in theform of events; and direct read, write and control operations in which aconsumer desires to read, write or control a specific tag or set oftags, providing a direct interface from consumer to provider.

In the filter, a software object is defined that is both a consumer anda provider. Accordingly, there is a provider external to the filter thatexposes and fulfills the IIDTagReporter interface. The filter receivesthat interface as a consumer, performs its process as it may desire andexposes the same interface to its own consumer. So the filter canperform an intermediate processing step that modifies the requestscoming down from above, modifies the responses or reports coming up frombelow, or both. So, the filter is an object that both fulfills andconsumers an IIDTagReporter interface.

FIG. 17 illustrates one example of a filter, a filter providing eventcleanup. Often readers present noisy data, or sometimes fail to includetags that are present. This is a typical failure mode of RFID, butapplications want clean data, and reliable tag reports. The filter,shown in the middle of FIG. 17, accumulates information over multiplereadings to determine which tags are reliable, and only reports reliabletags up to the application or consumer. The filter object intercepts rawscan reports from a lower level reader, performs processes to determinewhich scans are reliable, and reports only those reliable ones back upto the application. The filter does not interfere with read, write orcontrol operations from an application, these are passed through thefilter to the reader device without interference, as are responsesthereto, which are forwarded back to an application.

FIGS. 18-22 illustrate other tasks accomplished through use of filtersof the present invention. For instance, product look up, configurationinformation hiding hardware details, buffering data, producingstatistics and traffic reports, and aggregating multiple readers to looklike one single reader at a virtual level. Looking things up in adatabase, presenting a user interface, hopping over a network, can allbe couched as a filter.

FIG. 23 illustrates one embodiment of a filter-based architecture,showing development of an enterprise scale system, where filters are aprimary building block for an RFID application interface. A filter canbe as small as a single program sitting on a mobile device, or as largeas a program covering a database and presenting an interface with thedatabase. Accordingly, because the virtual reader design of the presentinvention consumes and exposes the same interface, the filters can bestacked, providing various outputs to various locations, and providingthat various elements be grouped onto one, or different computers, andthat a web service can be flexibly incorporated. The present inventiondiffers from a traditional approach, where you locate a web service andimplement it. In the present invention, a web service can be placed atany level, and can be relocated later in a different portion of thestack.

FIG. 21 illustrates Spanning the Network, or Network Hopping. In FIG.21, a stack of filters is shown at “server operations.” A web service isexposed, representing the reader plus its stack of filters through anetwork server exposing the web service. There is also a network clientthat accesses the web service. The client exposes to the application thesame IIDTagReporter interface used elsewhere, effecting a transparentconnection from the lower level stack on the reader (server operations)up to client operations, which views the reader as a server. What isprovided is a single stack that hops over the network. Further, therecould be many matches and many clients all connected to one server. So,a branch point is effectively provided. In FIG. 21, the network serverand network client represent two halves of a single filter. At thispoint, the IIDTagReporter interface can both consume and produce. Avariation is shown in the center of FIG. 21, where a stack comprises webservice building blocks. A reader might end with a network server piece,having a building block beginning to a network client, with a stack ontop of that, to an application beginning with a network client.

FIG. 22 illustrates Database-Hopping, where a stack is placed on thereader and ends with a proponent that loads data into a database. Anapplication that wishes to fetch data from the database uses an accessorobject, which is adequate for stored data, such as tag reports. However,if the application wants to perform a direct control operation, such asread or write, the accessor can expose the IIDTagReporter interface. Toperform a direct operation, the application uses the IIDTagReporterinterface to instruct the DB Accessor to perform the direct operation.The DB Accessor locates the DB loader and instructs of the operation.Locating the DB loader can be problematic, because of the difference intime between the direct operation and when the info was loaded, whichcould have occurred minutes ago, or hours ago. The present inventionprovides that the DB loader expose a web service that could be used bythe Accessor, and that web service could be stored in the database. Whenthe Accessor retrieves the data, it also has access to the URL. If theapplication requests a direct IO operation, the Accessor retrieves theURL, contacts that web service, which is the DB Loader, and tells the DBLoader what operation to perform. The DB loader can then communicate theoperation down to the reader.

FIG. 24 illustrates a Drop-Thru design for Tall Filter Stacks. One issuethat can arise with tall or long filter stacks is when a call originatesfrom a top level that must be sent to a bottom level. This call must beforwarded to a next lower level, then to the next lower level, and soon, until reaching the respective lower level. This results in manycalls, which are fast in operation, but are not free. It is thereforedesirable to minimize the number of calls, or steps. The presentinvention includes a mechanism whereby an application can instruct a toplevel filter of the requested instruction. The top level filter candispatch that operation directly down to the respective lower levelfilter that will implement that operation, thereby skipping allintermediate filter levels. Accordingly, all calls become a call of onlyone or two steps. A call is only one step if the top level filterreceiving the instruction can implement the operation. A call is twosteps if another level filter must implement the operation as receivedfrom the top level filter.

Similarly, the drop-through (or pass-through) mechanism can be used forevents returned from a reader and forwarded up (as rapidly as possible)to a desired consumer. The present invention implements the mechanism bymaking the filter object model slightly more complex than theIIDTagReporter. The filter is a subclass of IIDTagReporter, havingextensions, one of which is a table that records which level filteractually implements an event for every method, every event, and everyproperty. The table is constructed from the bottom to the top, so thatthe lowest level reader essentially implements everything. The lowestlevel filter uses the table, which informs that the reader implementsall operations, and only the methods implemented by the lowest levelfilter does the filter enter its own identity into the table. The tableis passed to the next lowest level filter, which uses the table asreceived except that it enters its identity in the table for eachmethod, property or event that it implements. As the table passes upthrough the level of stacks, objects are created and filters aresubstantiated. By the time the table reaches the top level filter, thetable is a completed directory of where the reader can dispatch all theevents that it receives.

A given level of filter need not consult the table if it implements amethod itself. A given level of filter need only consult the table forthose methods that it does not implement. However, a default objectdefinition for a filter would have the filter consulting the table forevery method, property and event. If a filter is created by subclassing,the filter object model would provide overrides for specific methods,properties and events and when created, will stamp its own ID onto thecorresponding elements of the table.

Further, each level of filter may have some additional parameters andcontrol operations relevant to its processing. By the time events arepassed up to an application, accumulation of passages can occur. So, itis not enough for a filter to simply pass through unique features frombelow, the filter must add and append its own unique features to thelist. Accordingly, name collisions could result; for example, if afeature is exposed with a same name as that from a lower level.Resolution must then occur, such as appending the name of the filterlevel to each property, method, feature, etc.

There are many different kinds of pass-throughs in the IIDTag model. Forexample, some tags can generate messages to the reader without beingscanned, known as tag generated events. Tag generated events can haveassociated data not understood by any component other than theparticular hardware. The middleware may have to pass the associateddata, and the tag generated event, all the way up to the application,even though the middleware doesn't know how to process the data.Accordingly, many unique features can arise at the tag level, and at thereader level. All of these features require extensions in order to bepropagated up to an application. Currently, the present inventionimplements the extensions by assimilating names of the respectivefeatures.

Accordingly, aspects of the invention, possibly implemented in software,include receiving scan activity instructions from one or more consumersregarding AutoID Tags, forwarding the instructions to one or moreproviders implementing the scan activity, receiving responses to theinstructions from the one or more providers and forwarding the responsesto the one or more consumers, both fulfilling and consuming an ID Tagreader interface.

The process could further include accumulating information over multiplescanning activities, determining which AutoID Tags scanned are reliablebased upon the information accumulated, and forwarding only responsesdirected to the reliable AutoID Tags to the one or more consumers. Thesefurther included tasks can be adapted to not interfere with any specificinstruction from a consumer to read, write or control one or morespecific AutoID Tags.

Any one or more of the following tasks could also be performed prior toforwarding the responses to the one or more consumer:

-   -   retrieving product data from a database based upon the responses        from the one or more providers;    -   parsing binary identification data into fields;    -   abstracting noisy response events into meaningful events;    -   configuring information to hide hardware details associated with        the one or more providers;    -   buffering data;    -   producing statistics and traffic reports based upon the        responses from the one or more providers;    -   aggregating multiple providers as one provider as viewed from        the one or more consumers;    -   hopping over a network, and    -   presenting a user interface to various services.

Further, the invention can define an interface stackable between one ormore consumers and providers, and multiple stacked interfaces canprovide multiple outputs and inputs for AutoID Tag manipulation betweenthe one or more consumers and providers.

In another aspect, computer-executable components include a providerthat implements a scan of one or more ID tags for retrieval ofinformation relevant to the ID tags, a consumer that receives and usesthe information relevant to the ID tags, and an interface providingcommunication between the provider and the consumer. The interface caninclude configuration parameters from the consumer to the provider,scanning activity instructions from the consumer to the provider, andprovider reports for the consumer.

Provider reports can include observations of the tags in a form ofevents and direct read, write and control instructions from the consumerdirected to a specific tag or set of tags, providing directcommunication from the consumer to the provider for the direct read,write and control instructions.

A plurality of interfaces can be included, where at least one interfaceis associated with the provider and at least one interface is associatedwith the consumer. Programming devices can exist between the pluralityof interfaces so that the programming device(s) receives the interfaceassociated with the provider as a consumer, and receives the interfaceassociated with the consumer as a provider, allowing the programmingdevice to perform intermediate processing steps, modifying requestscoming down from the consumer and responses or reports coming up fromthe provider, or both. The intermediate processing steps could include,among other things, the steps listed above.

Report evaluators and a database could also be included, allowing theprogramming device(s) to receive provider reports, accumulateinformation in the database over multiple receivings of providerreports, and determine which tags are reliable using the reportevaluator, providing a filtering where only reliable tags provided inthe provider reports are forwarded to the consumer.

Programming device performance can be adapted to not interfere withdirect read, write or control operations from an consumer, so that thedirect read, write or control operations are passed through theprogramming device to the provider without interference, and responsesthereto are passed through the programming device to the consumerwithout interference.

A plurality of programming devices could be included, where, in oneexample, at least two programming devices are stacked to allow adjacentcommunication with one another. In this example, one programming deviceexternal in the stack receives the interface associated with theprovider, and another programming device external in the stack receivesthe interface associated with the consumer. The stack of programmingdevices provides various outputs to various locations, provides thatvarious elements be grouped onto one or different computers, andprovides that a web service can be flexibly incorporated anywhere in thestack of programming devices.

The stacked programming devices also allow adjacent communicationbetween one another, so that a web service could be established betweentwo of the stacked programming devices, providing a transparentconnection between the stacked programming devices. The web servicecould include at least one network server and at least one networkclient communicating over a network, so that the stacked programmingdevices allow the stack of programming devices to hop over the network.

A database can also be included, along with a database loader inassociation with the provider, and a database accessor in associationwith the consumer, providing that, when the consumer requests a directcontrol operation concerning a tag and the consumer instructs thedatabase accessor to perform the direct operation through the interfaceassociated with the consumer, the database accessor instructs thedatabase loader, by way of the web service, to perform the directoperation with the database or the provider. The web service can bestored in the database and the database accessor can have access to aURL of the web service, so that the database accessor, to perform adirect operation, retrieves the URL, contacts the web service and thedatabase loader, and instructs the database loader to perform the directoperation.

Stacked programming devices also allow that one programming deviceexternal in the stack can receive the interface associated with theprovider (at a lowest level programming device), and that anotherprogramming device external in the stack can receive the interfaceassociated with the consumer (at a top level programming device), toprovide a pass-through mechanism that, when the consumer instructs thetop level programming device to perform an operation, the top levelprogramming device transmits the instruction directly to a respectivelower level filter that will implement the operation so thattransmission of the instruction does not require passage through allintermediate programming devices.

The pass-through mechanism can have stored thereon a data structureincluding extensions such as a table that records which level filterimplements a respective operation for every method, event, and propertypossibly tasked. The extensions could further include unique features ofa respective programming device, such as tag generated events.

ID Tag Reports

An IDTag Report is a record of an IDTag condition, situated at a giventime and place. Reports may be used to record the observations of radiohardware, the inferences derived from these observations, and currentbeliefs about the state of an IDTag.

An IDTagReportList holds a list of IDTagReport objects. While itpresents the list to users as an array, the internal representation usesArrayList so reports can be added easily as the IDTagReportList is beingcreated.

When it is being created, the IDTagReportList accumulates reports. As itdoes, it automatically keeps track of two circumstances:

-   -   If the reports are added in ascending order of ID (and timestamp        for equal IDs), then the IDTagReportList is considered to be        “sorted”. (Alternatively, the caller can use the Sort method to        sort the reports in ascending order by ID and timestamp.)    -   If all the reports have the same IDTag template, then this        property is copied into the IDTagReportList itself. Otherwise,        this property of the IDTagReportList will be null. Similarly,        the ID templates, conditions, sources, locations, and timestamps        of all the reports are compared, and if they are all the same,        then the corresponding property will be recorded in the        IDTagReportList. This way, an application can determine very        quickly what properties are in common among the reports in the        IDTagReportList.

An IDTagReportList is optimized for sequential processing, particularlyin order of increasing ID. However, it is sometimes desirable to processreports based on randomly ordered tag IDs. To facilitate this, theIDTagReportDictionary is a specialized IDTagReportList that alsosupports retrieving reports by tag ID, and deleting reports. It can bethought of as an IDTagReportList with an internal Hashtable that has thesame set of reports as contents, allowing both sequential and randomretrieval with high efficiency. Deletion is not especially efficient,however. An IDTagReportList can contain at most one IDTagReport for agiven ID; adding an additional report will overwrite any previouslystored report with the same ID.

CONCLUSION

The various techniques described herein may be implemented in connectionwith hardware or software or, where appropriate, with a combination ofboth. Thus, the methods and apparatus of the present invention, orcertain aspects or portions thereof, may take the form of program code(i.e., instructions) embodied in tangible media, such as floppydiskettes, CD-ROMs, hard drives, or any other machine-readable storagemedium, wherein, when the program code is loaded into and executed by amachine, such as a computer, the machine becomes an apparatus forpracticing the invention. In the case of program code execution onprogrammable computers, the computing device will generally include aprocessor, a storage medium readable by the processor (includingvolatile and non-volatile memory and/or storage elements), at least oneinput device, and at least one output device. One or more programs thatmay utilize the creation and/or implementation of domain-specificprogramming models aspects of the present invention, e.g., through theuse of a data processing API or the like, are preferably implemented ina high level procedural or object oriented programming language tocommunicate with a computer system. However, the program(s) can beimplemented in assembly or machine language, if desired. In any case,the language may be a compiled or interpreted language, and combinedwith hardware implementations.

While the present invention has been described in connection with thespecific examples in conjunction with the various figures, it is to beunderstood that other embodiments may be used or modifications andadditions may be made to the described embodiments for performing thesame function of the present invention without deviating therefrom. Theexamples are offered in explanation of the invention and are in no wayintended to limit the scope of the invention as defined in the claims.In summary, in no way is the present invention limited to the examplesprovided and described herein. Therefore, the present invention shouldnot be limited to any single embodiment, but rather should be construedin breadth and scope in accordance with the appended claims.

1. A method for managing ID tag scanning and reporting, the methodcomprising the steps of: initiating a scan of one or more tags;instructing a collection of ID signals transmitted as a result ofinformation gathered during the scan, the ID signals including a tagidentifier for each tag; instructing a performance of one or more of thefollowing prior to generating and forwarding a scan report to anapplication: a) where the tag identifier is a temporary tag identifier,resolving the temporary tag identifier for each tag to a permanent tagidentifier; b) looking up an actual object model for each tag using thetag identifier; c) authenticating each tag; d) gathering and storing alldescriptive information available for each tag; and e) recognizing anychecktags and generating an associated alert; and generating andforwarding a scan report to an application.
 2. The method of claim 1,wherein a reader is instructed to resolve the temporary tag identifierfor each tag to a permanent tag identifier (step (a)) prior toperforming any subsequently listed step.
 3. The method of claim 1,wherein resolving the temporary tag identifier to a permanent tagidentifier for each tag includes forwarding a security key to therespective tag to receive the permanent tag identifier.
 4. The method ofclaim 1, wherein looking up the actual object model for each tag usingthe tag identifier is performed in the application.
 5. The method ofclaim 1, wherein looking up the actual object model for each tag usingthe tag identifier is performed in the reader.
 6. The method of claim 1,wherein the method operates in a RFID system.
 7. The method of claim 1,wherein checktags are a list of one or more tag identificationsgenerated by the application and forwarded to a reader with instructionthat if any of the tag identifications are recognized during a scan aspecial alert is to be forwarded to the application and the respectivetag identification is, or is not, to be included in the scan report tothe application.
 8. The method of claim 1, wherein checktags are a listof one or more tag identifications generated by the application andforwarded to a reader with instruction that if any of the tagidentifications are not recognized during a scan a special alert is tobe forwarded to the application and the respective tag identificationis, or is not, to be included in the scan report to the application. 9.The method of claim 1, further comprising the step of instructing thesuspension of further scanning pending further instruction, allowinginteraction with one or more tags prior to a resetting of temporaryidentification information upon a further scan.
 10. The method of claim1, wherein all of steps (a) through (e) are performed prior togenerating and forwarding the scan report to the application.
 11. Themethod of claim 1, wherein an application instructs a reader to performan entire scan activity, including instruction to perform one or more ofsteps (a) through (e), based upon a correlating triggering condition.12. A computer-readable medium having computer-executable instructionsfor performing steps comprising: initiating a scan of one or more tags;instructing a collection of ID signals transmitted as a result ofinformation gathered during the scan, the ID signals including a tagidentifier for each tag; instructing a performance of one or more of thefollowing prior to generating and forwarding a scan report to anapplication: a) where the tag identifier is a temporary tag identifier,resolving the temporary tag identifier for each tag to a permanent tagidentifier; b) looking up an actual object model for each tag using thetag identifier; c) authenticating each tag; d) gathering and storing alldescriptive information available for each tag; and e) recognizing anychecktags and generating an associated alert; and generating andforwarding a scan report to an application.
 13. The computer-readablemedium of claim 12, wherein a reader is instructed to resolve thetemporary tag identifier for each tag to a permanent tag identifier(step (a)) prior to performing any subsequently listed step.
 14. Thecomputer-readable medium of claim 12, wherein resolving the temporarytag identifier to a permanent tag identifier for each tag includesforwarding a security key to the respective tag to receive the permanenttag identifier.
 15. The computer-readable medium of claim 12, whereinlooking up the actual object model for each tag using the tag identifieris performed in the application.
 16. The computer-readable medium ofclaim 12, wherein looking up the actual object model for each tag usingthe tag identifier is performed in the reader.
 17. The computer-readablemedium of claim 12, wherein checktags are a list of one or more tagidentifications generated by the application and forwarded to a readerwith instruction that if any of the tag identifications are recognizedduring a scan a special alert is to be forwarded to the application andthe respective tag identification is, or is not, to be included in thescan report to the application.
 18. The computer-readable medium ofclaim 12, having further computer-executable instructions for performingthe step of instructing the suspension of further scanning pendingfurther instruction, allowing interaction with one or more tags prior toa resetting of temporary identification information upon a further scan.19. The computer-readable medium of claim 12, wherein all of steps (a)through (e) are performed prior to generating and forwarding the scanreport to the application.
 20. The computer-readable medium of claim 12,wherein an application instructs a reader to perform an entire scanactivity, including instruction to perform one or more of steps (a)through (e), based upon a correlating triggering condition.
 21. Thecomputer-readable medium of claim 12 having stored thereon a datastructure comprising one or more quality-of-service fields describingimportance parameters to a tag reader of a quality of pre-determinedactivities relative to speed of completion of the activity.
 22. Thecomputer-readable medium of claim 21, wherein the parameters govern anyof: elimination of false negatives (missed tags) in scan operations;elimination of false positives (ghosts) in scan operations; confidencethat read operations have succeeded; confidence that write operationshave succeeded; confidence that a tag is authentic (not counterfeit);maximum packing of data into an available user-memory on a tag; maximumrange for communicating with tags; number of tags in communication rangeof a tag reader; and precision of location information of a tag.
 23. Thecomputer-readable medium of claim 21, wherein the importance parametershave one of the following values: less important than speed; asimportant as speed; more important than speed; and most critical.